Agent-driven install path, Windows clarity, onboarding cost+inject prompts#853
Conversation
Correct stale 51-tool references to the registry truth of 53 across the standalone shim comments and the registry comment, derive the visible tool count from the registry, update README test-count stats to 1,423+, add the demo --serve README line, and add a vitest guard that fails CI if the registry count, README, or CLI help drift out of sync.
Convert the hard process.exit on a PATH iii version mismatch into a non-fatal warning so a mismatched iii on PATH no longer blocks first run; agentmemory continues with its own pinned engine in ~/.agentmemory/bin and honors AGENTMEMORY_III_VERSION. Add a --serve flag to the demo subcommand that boots the server, waits for health, runs the seed and query demo, and tears the server down on exit, all in one invocation. Derive the --tools help counts from the registry.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Add INSTALL_FOR_AGENTS.md, a runbook a coding agent can execute end to end: global install, start server, demo --serve, connect MCP, install skills, and a save/recall verification round-trip. README Install section now leads with the agent one-liner path and a short Windows callout (WSL2 is the fast path, native setup is manual and connect is unsupported there). Onboarding gains a context-injection step that asks whether to enable AGENTMEMORY_INJECT_CONTEXT with a token-cost note, persists the choice as a never-nag prefs flag, and writes the env var when enabled. Provider selection prints a one-line rough cost hint.
rohitg00
force-pushed
the
feat/agent-onboarding
branch
from
3828346 to
30e64ee
Compare
1 participant
Stacks on #852 (base
fix/onboarding-trust). Agent-driven onboarding and cross-platform clarity.Changes
Agent-driven install path. New
INSTALL_FOR_AGENTS.mdat the repo root: a tight, imperative runbook a coding agent can execute end to end. Steps cover global install (npx + EACCES sudo fallback), starting the server,agentmemory demo --serveas the one-shot proof, detecting the calling agent and wiring MCP viaagentmemory connect <agent>(lists the supported agent names), installing native skills, a health check plus amemory_saveandmemory_smart_searchround-trip for verification, and a final success report. README Install section now leads with a single recommended one-liner that hands a coding agent the raw URL of that runbook as the fastest path.Windows clarity. A short, visible callout near the top of the Install section: on Windows the fast path is WSL2; native engine setup is manual (about 10 to 20 minutes) and
agentmemory connectis currently unsupported there. Links to the existing detailed Windows notes lower in the README.Wizard context-injection step. Onboarding now asks whether to enable automatic context injection (
AGENTMEMORY_INJECT_CONTEXT) so the agent recalls past sessions without being asked, with a one-line token-cost note (default off). The choice is persisted as a never-nag prefs flag (matching the existing skip-flag pattern), the env var is written into~/.agentmemory/.envwhen enabled, and the non-TTY/CI skip path is honored.Provider cost note. The LLM provider selection step prints a one-line rough cost hint for the chosen provider, mirroring the cost-aware info in the README Configuration section. Inline note only, no matrix.
Validation
npm run buildpasses.onboarding,cli-onboarding,preferences,consistency(19 tests).